Use dedicated modules for single and multiple entity query hooks.

Ensure when cloning and deleting tickets via their query hooks a
notification message is displayed.

Use dedicated describe blocks for each hook and use real model instances
in the tests.

Ensure when cloning and deleting users via their query hooks a
notification message is displayed.

Allow to query Target data via use query hooks.

As query hooks might not return a response object and instead the data
directly the goToDetails function needs to support this use case.

Refactor TargetComponent to use the new query hooks for target.

Before the changed port list was re-loaded after a port range was
deleted. This is completely unnecessary and also created several
additional requests when a user deleted several port ranges in the
dialog.

Allow to query and mutate port lists via query hooks.

Use the new port list query hooks within the PortListComponent.

Implement the basic set of query hooks for credentials.

Update TargetComponent and TargetDialog to use the new port list and
credential query hooks internally instead of directly querying the gmp
API.

Entity and entities queries are separated everywhere else already.

For deleting a user an additional input argument is required.

It's not required for GMP.

…ssage

Ensure that the name argument is passed by default and the type checker
complains about it. This ensure the success message is displayed
correctly.

Use useDeleteMutation and adapt arguments to recent changes.

One for tag and one for tags queries.

One for agent and one for agents queries.

All save methods of commands should just return a Promise<void> because
it just updates the current entity.

This new interface will be re used in a query hook.

Always behave the same for all single entity query hooks. Clone and
create return EntityActionData. Save and delete just return void.